Boeing Security Guidelines for using WebEx 
For non-Boeing attendees
 
 

General security features

The Boeing WebEx service provides the following security features:

  • Transmissions between your computer and the WebEx servers are encrypted using SSL encryption.  Your browser must be configured for 128-bit encryption to meet Boeing security requirements.
  • Meetings scheduled on the Boeing WebEx site are unlisted and cannot be viewed by others.
  • A meeting number and password are required to join a meeting.
  • No meeting data is permanently stored on the WebEx system.
  • WebEx personnel cannot monitor meetings in progress.

Security guidelines for sharing data 

Important! The following guidelines apply to sharing Boeing data on the Boeing WebEx site.  Before sharing your company's data in a Boeing meeting, consult your company's computing security policies to determine what data can be shared. 

  • The Boeing Computing Security and Export Compliance groups have approved the Boeing WebEx service for sharing sensitive and non-sensitive Boeing information.  This includes the following categories:
    • Boeing Proprietary
    • Boeing Limited
    • Export Controlled (ITAR/EAR)
    • Third-Party Proprietary 
    • Competition Sensitive
    • Business and Technical
    • Non-sensitive
  • Do not share classified information on this service. See the appropriate documentation for procedures on the proper handling of classified information. 

Browser encryption requirements

All participants' browsers must be configured for 128-bit encryption.
 

Protecting meeting numbers and passwords

The Boeing meeting host will send you the meeting number and password for the WebEx meeting:

  • The meeting number and password are confidential information.  Protect the meeting number and password so others will not learn this information.
  • If you place the meeting number and password on your electronic (e.g., Outlook) calendar, then select the Private setting on your meeting notice.

Copyright ã The Boeing Company

Revised:  February 19, 2004